Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency dts-bundle-generator to v9 #2141

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 28, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
dts-bundle-generator ^6.13.0 -> ^9.5.1 age adoption passing confidence

Release Notes

timocov/dts-bundle-generator (dts-bundle-generator)

v9.5.1: 9.5.1

Compare Source

Fixed

v9.5.0: 9.5.0

Compare Source

Fixed
  • Constants declared by using object/array binding pattern syntax fail the build (see #​315 and #​317)

v9.4.1: 9.4.1

Compare Source

Fixed
  • Fixed issue when because of recursive types some of the types could get removed from the bundle (see #​318 and 897a5d5)

v9.4.0: 9.4.0

Compare Source

Fixed
  • Performance improvements (see #​302, #​303 and #​314)
  • Declarations of "unknown" modules aren't included despite enabled inlineDeclareExternals flag (see #​312 and 186e6fd)
  • Fixed handling import * statements with local usage but not directly exporting (see #​304 and #​309)
  • Fixed bug when imported nodes weren't included into bundle if they were used in declare module statements only (see #​305 and #​316)
  • Fixed issue with unknown extension when using allowArbitraryExtensions compiler option (see #​313) - thanks @​stepankuzmin

v9.3.1: 9.3.1

Compare Source

Fixing one little oopsie from v9.3.0 release.

Fixed
  • Spamming warning log messages while processing variables (see 8ecb56f)

v9.3.0: 9.3.0

Compare Source

Changed
  • Do not compile bundled output together as they might have incompatible global declarations (see #​296 and 43c2058)
Fixed
  • Not all symbols in a declaration merging are exported (see #​301 and 874f801)
  • Namespaced imports/exports don't generate a namespace if they are exported via name (see #​299 and 86fc2ff)
  • jsdoc comments are stripped for nodes that were renamed because of the name collision (see #​298 and 2b1b281)
  • Do not rename a node if known global name refers to this a symbol of that node (see #​297 and c0a7007)

v9.2.5: 9.2.5

Compare Source

Fixed
  • Fixed inlining transitive-dependencies when using inlineDeclareGlobals (see eb03676)

v9.2.4: 9.2.4

Compare Source

Added

v9.2.3: 9.2.3

Compare Source

Fixed
  • Do not export types if their local name changed because of collisions (unless they were explicitly exported) (see #​286 and 643003f)

v9.2.2: 9.2.2

Compare Source

Fixed

v9.2.1: 9.2.1

Compare Source

Fixed
  • Fixed handling globalThis and undefined (as a value) values (see #​282 and 6a132dd)

v9.2.0: 9.2.0

Compare Source

Release notes

In this release I tried to adapt tests from api-extractor tool in order to compare results and apart from some passing tests I found a few issues that are fixed in this release.

Fixed
  • Prettified output when some "parts" aren't emitted (e.g. banner) (see af1736f)
  • Fixed incorrect import() statement if imported name is imported with renaming (see 9edab0d)
  • Fixed wrongly collision-resolved names when a name exists in a global scope (see 25703d7)
  • Fixed incorrect output while having re-export via import (see e324b37)
  • Fixed incomplete generated namespace while having export * from statements (see 0bd1a19)
  • Fixed incorrect generation while using export * from statements (see 0bdbf07 and b27daaa)
  • Fixed error while generating namespaced exports via import statements (see 06e531f)

v9.1.0: 9.1.0

Compare Source

Release notes

With this release all known bugs in the tool are fixed (especially long-lived ones!) 🎉

Fixed
  • Star re-exports (import * as NS / export * as NS) aren't wrapped with a NS name (see #​134 and #​281)
  • (Re-)Export from re-export from external library doesn't add import/export statements (see #​251 and #​279)

v9.0.0: 9.0.0

Compare Source

Release notes

This release is one of biggest and the most valuable releases in years.

It introduces a fix for a limitation that existed since very first release i.e. resolving of name collisions 🎉.

Now, if you have 2 nodes with the same name in the bundle, one of them will be renamed (by adding $NUM suffix) to avoid clashing and accidental declaration merging (but if you have 2 interfaces declared in the same module to have declaration merging it should work as expected too).

Because of this new mechanism it helped to address some of the issues that I wasn't aware of but it seems that it existed in some of the packages, i.e. using a wrong name because of renaming during import (import { name as newName } case) (see "Additional information" section in this PR).

One of known changes in the declaration generation with this release is that a function/class/etc that was originally exported with the default export will never be exported directly but via re-export export { name as default }. This should not affect the result of the bundle but I think it is worth to note it.

But there is more, please refer to the change log below.

Last but not least, I want to thank @​Atrue for the contribution which was a motivation to make this release happen 🙏

Added
  • Use language service "rename" functionality to avoid name collisions (see #​130 and #​270)
  • Support for auto renaming nodes with the same name in the bundle (see #​116 and #​270)
Fixed
  • Inlining a library with namespaced imports/exports inlines export statements (see #​271 and #​278)
  • Incorrect handling re-export with namespace (see #​274 and #​277)
  • Double-underscored names aren't exported (see #​275 and #​276)
  • Invalid bundle while using import as statements in the code (see #​184 and #​270)
  • Incorrect handling namespaced imports/exports (see #​266)

v8.1.2: 8.1.2

Compare Source

Fixed
  • Something went wrong - value cannot be null (see #​265 and #​267)

v8.1.1: 8.1.1

Compare Source

Fixed
  • Stack overflow while handling re-exports with circular dependencies (see #​264 and 4429eac)

v8.1.0: 8.1.0

Compare Source

Added
  • Added support for .mts and .cts extensions (see #​204)
  • Fixed handling re-exports in dependencies (see #​259)

v8.0.1: 8.0.1

Compare Source

Fixed
  • declare module Module statements from dependencies are inlined despite if it should be imported (see #​250 and a725512)

v8.0.0: 8.0.0

Compare Source

Breaking changes
  • Minimal typescript version changed from 4.0 to 5.0 (see #​238 and #​240)
  • Changed default behavior for module ModuleName statements (without quotes) (see #​237 and #​242)
Fixed
  • Fixed wrong export state of referenced namespaces/modules (see #​241 and #​242)
  • Some types are removed if they used in ambient context (see #​243 and #​244)
  • Imports are lost when importing esm-like modules without default export using commonjs import or esm import default (see #​230 and #​245)
  • Statements aren't inlined if they are used in declare global statements only (see #​214 and #​246)
  • Fixed incorrect output if rename while re-exporting the default export without a name (see #​185 and #​248)

v7.2.0: 7.2.0

Compare Source

Fixed
  • Incorrect handling inlining import() statements (see #​234 and #​235)

v7.1.0: 7.1.0

Compare Source

Fixed
New Contributors

Full Changelog: timocov/dts-bundle-generator@v7.0.0...v7.1.0

v7.0.0: 7.0.0

Compare Source

Breaking changes
  • Minimal typescript version changed from 3.0 to 4.5
  • yargs dependency was upgraded from 17.2 to 17.6
  • Minimal NodeJS version changed from 12 to 14
  • Compilation target changed from es5 to es2020 (modules are still commonjs though)

See #​224

Fixed
  • Improve support of non-relative imports in projects with a baseUrl (see #​224)

Many thanks to @​josh- for their contribution!


Configuration

📅 Schedule: Branch creation - "* 0-3 * * *" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the renovatebot label Nov 28, 2023
@renovate renovate bot force-pushed the renovate/dts-bundle-generator-9.x branch 3 times, most recently from 624e562 to de2603f Compare December 30, 2023 10:23
@renovate renovate bot force-pushed the renovate/dts-bundle-generator-9.x branch 2 times, most recently from db2d3da to 249807b Compare January 11, 2024 22:48
@renovate renovate bot force-pushed the renovate/dts-bundle-generator-9.x branch from 249807b to 9d34f24 Compare January 25, 2024 21:35
@renovate renovate bot force-pushed the renovate/dts-bundle-generator-9.x branch from 9d34f24 to 3c422f8 Compare February 3, 2024 21:56
@renovate renovate bot force-pushed the renovate/dts-bundle-generator-9.x branch 3 times, most recently from a7f8517 to dbac8d6 Compare April 18, 2024 02:08
@renovate renovate bot force-pushed the renovate/dts-bundle-generator-9.x branch from dbac8d6 to ec41c36 Compare April 22, 2024 00:26
@renovate renovate bot changed the title chore(deps): update dependency dts-bundle-generator to v9 chore(deps): update dependency dts-bundle-generator to v9 - autoclosed Dec 8, 2024
@renovate renovate bot closed this Dec 8, 2024
@renovate renovate bot deleted the renovate/dts-bundle-generator-9.x branch December 8, 2024 19:00
@renovate renovate bot changed the title chore(deps): update dependency dts-bundle-generator to v9 - autoclosed chore(deps): update dependency dts-bundle-generator to v9 Dec 10, 2024
@renovate renovate bot reopened this Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants